Protocols for naming files:

(Note:Omni files are an exception to these rules. They are automatically named according to the project title, and there is no need to create duplicates.)

When assigning names to files, three things should be kept in mind: The project name, the type of work the file contains, and the volume that the file belongs to. Spaces aren’t allowed in file names, so “_” should be used between these three things instead. As an example, when naming files in the Pinky project, the file name would always start with “Pinky”. A synaptic annotation file for Vol. 30 in Pinky will be named “Pinky_Synapses_Vol.30”.

        There will be situations where multiple copies of a file will be made. This could be because someone wants to experiment without saving over the output file, or because multiple people are training on the same data set. In these instances, the tracer’s name should be included as well as a word or two indicating if the file is for practice or for an experiment. For example, if Ben wants to test organization of segments in the segment tree in a semantic annotation Vast file that belongs to Pinky vol.202, he would label it “Pinky_Annotation_vol.202_Ben_Experiment.” There is an  archive folder in each project. All practice or experiment sets should be saved in this folder. Regarding duplicates of files that have been created as a kind of saved state assurance, they should be archived in the Archive Folder as well. Once the task in question has been completed, it is necessary to cleanup the folder to ensure that, each file is stored in the appropriate folder.

        There will be projects that as of yet have not been worked on, and so naming protocol hasn’t been nailed down. For now, any other relevant information should be added to the end of the file name.

        “Project name_Type of work_Volume(if applicable)_Any other relevant information”

EXAMPLES